Release notes

2026r2

Changes to support linear EPG workflow using publication API

Customers typically publish their Electronic Program Guides (EPG) for linear channels using file-based reports or open APIs combined with change detection logic for recent updates. However, this is more cumbersome than a direct pull-based interface such as a BAPI that allows them to fetch publication data efficiently. Up until now, the publication API was mostly intended for on-demand publication and did not support channel filtering, which limited usability for linear purposes.

From this version, the publication API has been extended to support linear EPG use cases.

Firstly, additional filter parameters can now be added to the URL of the GET /publication-snapshots search request to differentiate EPG data for the linear publication workflow more clearly:

  • channel:
    Filter on a specific channel. For

    • linear publication snapshots, this should be the API reference of the original linear channel.

    • on-demand publication snapshots, this should be the API reference of the publication channel.

    • To retrieve the API reference, the GET /channels drop-down request of the linear schedule or on-demand schedule API can be used.

  • publicationStartDate:
    Filter on the start date of snapshots, using the format YYYY-MM-DD.
    This attribute was already available in the response of the GET /publication-snapshots/{publicationSnapshotId}.

  • publicationKind:
    Filter on the publication system kind. The possible values are linear and onDemand.

The publicationKind attribute uses the same values as the kind filter used in the GET /publication-systems request. Previously, these were press and onlinePublication, but they have also been changed to linear and onDemand.

An example of a URL with one of the new filters: GET /publication-snapshots?filter=eq(publicationKind,onDemand)

Secondly, additional attributes were added to the responses of the GET /publication-snapshots/{publicationSnapshotId} and GET /publication-snapshots requests:

  • channel: This returns the API reference of the linear or the publication channel.

  • publicationKind: The kind of the publication system: linear of onDemand.

  • punchline2

  • punchline2ForSeries

  • punchline3

  • punchline3ForSeries
    The additional punchlines of a publication record.

An example of the response of the GET /publication-snapshots/{publicationSnapshotId} request:

{
    "publicationSnapshotId": "9056721669",
    "announcedTime": null,
    "channel": "MGX",
    ...
    "lastPublishedOn": "2023-06-07T09:50:34+02:00",
    ...
    "publicationEndDate": "2022-08-01",
    "publicationEndTime": "23:59:59.000",
    "publicationKind": "linear",
    "publicationStartDate": "2022-08-01",
    "publicationSystemId": "16940000",
    "punchlines1": {
        "punchline1": "NL"
    },
    "punchlines1ForSeries": {
        "punchline1ForSeries": null
    },
    "punchlines2": {
        "punchline2": "NL"
    },
    "punchlines2ForSeries": {
        "punchline2ForSeries": null
    },
    "punchlines3": {
        "punchline3": "NL"
    },
    "punchlines3ForSeries": {
        "punchline3ForSeries": null
    },
  ...
}

API developers

The YAML has been updated for these changes. The latest version can be retrieved by using the GET /api call.

Changes:Closed
At line 136, the channel, publicationKind and publicationStartDate were added to the filter parameters of the get publication-snapshots call.
At line 593, the punchlines3ForSeries was added to the properties of the publicationSnapshot schema.
At line 718, the channel was added to the properties of the publicationSnapshot schema.
At line 750, the publicationKind was added to the properties of the publicationSnapshot schema.
At line 779, the punchlines3 was added to the properties of the publicationSnapshot schema.
At line 812, the punchlines2ForSeries was added to the properties of the publicationSnapshot schema.
At line 860, the punchlines2 was added to the properties of the publicationSnapshot schema.
At line 937, the values of the kind property of the publicationSystem schema were adapted.
At line 939, schemas were added for the new punchlines. At other places in the YAML, existing objects were reordered.

For easier viewing, the YAMLs can also be compared here: TextCompare